Click Here!
home account info subscribe login search My ITKnowledge FAQ/help site map contact us


 
Brief Full
 Advanced
      Search
 Search Tips
To access the contents, click the chapter and section titles.

Wireless Networking Handbook
(Publisher: Macmillan Computer Publishing)
Author(s): Jim Geier
ISBN: 156205631x
Publication Date: 09/01/96

Bookmark It

Search this book:
 
Previous Table of Contents Next


The WBS, schedule, and resource plan provide the basis for determining the cost of the project. Before estimating the cost, you will need to assign resources to each WBS task. In other words, identify who will be managing and performing the work for each task and indicate any necessary materials. The next step is to calculate labor and material (including travel) costs for each task, phase, and the entire project. Again, you might need to perform at least a preliminary requirements assessment and design before being able to determine costs associated with the hardware and software of the system being implemented.

During the execution of the project, you will need to track whether the project is being completed within budget. To facilitate budget control, assign unique account codes to project phases and subcodes to each WBS task. During the planning stages of the project, the initial budget is likely to be merely an estimate. After completing the requirements and design stages, the team might need to adjust the budget to reflect more precise information. Figure 5.8 identifies the major items of a project budget.


Figure 5.8  The major items of a project budget.

Defining Project Operations

The project scope, work plan, schedule, resources, and budget are the physical makeup of the project. To ensure a project runs smoothly, however, you should also define project operations by developing an operations plan. This plan covers the rules and practices people should follow during the project.

What aspects of the project should the operations plan cover? Generally, you should specify procedures for project actions that need to be followed each time the action is required. For instance, you should include these items in the operations plan:

  Roles and responsibilities of team members
  Methods for coordinating with other organizations
  Staffing procedures
  Travel policies
  Engineering drawing standards
  Document sign off procedures

To develop a project operations plan, review existing corporate and local policies and regulations, then define procedures for items that team members must accomplish in a unique manner. Also, be sure to identify any restrictions that corporate policies and other regulations place on the project.

Dealing with Project Risks

The success of a project is often jeopardized by unforeseen elements that crop up at inopportune times. The nasty truth is that many projects are not completed on time, within schedule, or as expected. As an example, a project team might successfully complete the design stage of the project and be ready to purchase the components when they discover the customer’s upper management has lost interest in the project and has withheld further funding. Or, you do a thorough job of defining user needs and then the team is not successful at determining a set of technologies and products that will fulfill the requirements.

To maximize the success of a project, the project team must not only develop a WBS, schedule, and resource plan, but also continually identify and manage risks. Risk management should begin early in the project, even during the planning stage, then continue throughout the project. A risk factor usually has more impact if you don’t attempt counter measures until later in the project. To avoid negative consequences, the team can manage risks by identifying risk factors and determining methods to reduce them. A risk factor is anything that might have adverse effects on the outcome of the project.

Here are examples of risks factors you should consider:

  Project Factors
  Clarity of project objectives
  Project team size
  Working relationships among project team members
  Team geographical disbursement
  Project duration
  Delivery date constraints
  Project manager’s prior experience
  Resource Factors
  Experience of project team members
  Team learning curve
  Use of contractors
  Potential loss of team members due to other projects
  Organizational Risk Factors
  Level of management commitment
  Funding constraints
  Level of user involvement and support during the project
  Firmness of benefits
  Length of time necessary to receive a return on investment for implementing the project
  Technical Factors
  Range of technologies and products available to satisfy requirements
  Complexity of the interfaces to existing systems
  Familiarity and prior experience with the type of implementation the team is accomplishing

You can control risks by following these steps:

1.  Review the project’s WBS, schedule, resource plan, and budget and assess the status of the preceding potential risk factors.
2.  Define the potential impact each risk has on the successful completion of the project.
3.  Pinpoint the causes of the risks.
4.  Refine the work plans to reflect the risk reduction strategy.
5.  Periodically reevaluate the potential risk factors, especially those found earlier in the project, and take necessary counteractive measures.

Creating the Project Plan

Before placing the project in full motion, you should collect all the individual planning elements and create a project plan as shown in figure 5.9. This could be as simple as putting a cover around the planning documents you already prepared. You can use the project plan to effectively manage the project through all phases.


Figure 5.9  The project plan.

Most organizations require a review and approval of the project plan by upper management before executing the project. As a final check before giving your project plan to an executive, use the following list to be certain the project plan:

  Has a project scope identifying clear objectives and business needs.
  Contains a work breakdown structure that covers all activities necessary to accomplish the project’s objectives.
  Contains a work breakdown structure that is detailed enough to accurately define the schedule and budget.
  Spells out a schedule that is realistic.
  Identifies a project team with team members who are available when needed and have the experience necessary to successfully complete the project.
  Identifies needed material resources, such as software tools and travel.
  Contains a budget with accurate costs.
  Adequately defines the roles and responsibilities of team members.
  Defines all risk factors that might impact the project, as well as actions needed to counteract the risks.


Previous Table of Contents Next


Products |  Contact Us |  About Us |  Privacy  |  Ad Info  |  Home

Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc.
All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited. Read EarthWeb's privacy statement.